Method and apparatus for uplink transmission using MIMO in wireless communication system

ABSTRACT

A method of a terminal in a wireless communication system is provided. The terminal includes receiving, from a base station, configuration information for a first uplink and configuration information for a second uplink, determining a first maximum number of multi-input and multi-output (MIMO) layers for the first uplink, based on the configuration information for the first uplink, determining a maximum number of layers for a physical uplink shared channel (PUSCH) supported by the terminal to be a second maximum number of MIMO layers for the second uplink, and transmitting, to the base station, the PUSCH by using at least one of the first uplink or the second uplink, based on the determined first maximum number of MIMO layers and the second maximum number of MIMO layers.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is based on and claims priority under 35 U.S.C. §119(a) of a Korean patent application number 10-2019-0099835, filed onAug. 14, 2019, in the Korean Intellectual Property Office, thedisclosure of which is incorporated by reference herein in its entirety.

BACKGROUND 1. Field

The disclosure relates to methods and apparatuses for configuring MultiInput Multi Output (MIMO) for supporting an uplink in a mobilecommunication system.

2. Description of Related Art

To meet increasing demand with respect to wireless data traffic afterthe commercialization of 4^(th) generation (4G) communication systems,efforts have been made to develop 5^(th) generation (5G) or pre-5Gcommunication systems. For this reason, 5G or pre-5G communicationsystems are called ‘beyond 4G network’ communication systems or ‘postlong term evolution (post-LTE)’ systems. To achieve high data rates, theimplementation of 5G communication systems in an ultra-high-frequency ormillimeter-wave (mmWave) band (e.g., a 60 GHz band) is being considered.To reduce path loss of radio waves and increase a transmission distanceof radio waves in the ultra-high frequency band for 5G communicationsystems, various technologies such as beamforming, massivemultiple-input and multiple-output (massive MIMO), full-dimension MIMO(FD-MIMO), array antennas, analog beamforming, and large-scale antennasare being studied. To improve system networks for 5G communicationsystems, various technologies such as evolved small cells, advancedsmall cells, cloud radio access networks (cloud RAN), ultra-densenetworks, device-to-device (D2D) communication, wireless backhaul,moving networks, cooperative communication, coordinated multi-points(CoMP), and interference cancellation have been developed. In addition,for 5G communication systems, advanced coding modulation (ACM)technologies such as hybrid frequency-shift keying (FSK) and quadratureamplitude modulation (QAM) (FQAM) and sliding window superpositioncoding (SWSC), and advanced access technologies such as filter bankmulti-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparsecode multiple access (SCMA), have been developed.

The Internet has evolved from a human-based connection network, wherehumans create and consume information, to the Internet of things (IoT),where distributed elements such as objects exchange information witheach other to process the information. Internet of everything (IoE)technology has emerged, in which the IoT technology is combined with,for example, technology for processing big data through connection witha cloud server. To implement the IoT, various technological elementssuch as sensing technology, wired/wireless communication and networkinfrastructure, service interface technology, and security technologyare required and, in recent years, technologies related to sensornetworks for connecting objects, machine-to-machine (M2M) communication,and machine-type communication (MTC) have been studied. In the IoTenvironment, intelligent Internet technology (IT) services may beprovided to collect and analyze data obtained from connected objects tocreate new value in human life. As existing information technology andvarious industries converge and combine with each other, the IoT may beapplied to various fields such as smart homes, smart buildings, smartcities, smart cars or connected cars, smart grids, health care, smarthome appliances, and advanced medical services.

Various attempts are being made to apply 5G communication systems to theIoT network. For example, technologies related to sensor networks, M2Mcommunication, and MTC are being implemented by using 5G communicationtechnology including beamforming, MIMO, and array antennas. Applicationof the cloud RAN as the above-described big data processing technologymay be an example of convergence of 5G communication technology and IoTtechnology.

As various services may be provided according to the foregoing and thedevelopment of mobile communication systems, methods for smoothlyproviding such services are required.

The above information is presented as background information only toassist with an understanding of the disclosure. No determination hasbeen made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the disclosure.

SUMMARY

Aspects of the disclosure are to address at least the above-mentionedproblems and/or disadvantages and to provide at least the advantagesdescribed below. Accordingly, an aspect of the disclosure is to providedapparatuses and methods capable of effectively providing services inmobile communication systems.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented embodiments.

In accordance with an aspect of the disclosure, a method of a terminalin a wireless communication system is provided. The method includesreceiving, from a base station, configuration information for a firstuplink and configuration information for a second uplink, determining afirst maximum number of multi-input and multi-output (MIMO) layers forthe first uplink, based on the configuration information for the firstuplink, determining a maximum number of layers for a physical uplinkshared channel (PUSCH) supported by the terminal to be a second maximumnumber of MIMO layers for the second uplink, and transmitting, to thebase station, the PUSCH by using at least one of the first uplink or thesecond uplink, based on the determined first maximum number of MIMOlayers and the second maximum number of MIMO layers.

In accordance with another aspect of the disclosure, a terminal in awireless communication system is provided. The terminal includes atransceiver, and at least one controller configured to receive, from abase station, configuration information for a first uplink andconfiguration information for a second uplink, determine a first maximumnumber of multi-input and multi-output (MIMO) layers for the firstuplink, based on the configuration information for the first uplink,determine a maximum number of layers for a physical uplink sharedchannel (PUSCH) supported by the terminal to be a second maximum numberof MIMO layers for the second uplink, and transmit, to the base station,the PUSCH by using at least one of the first uplink or the seconduplink, based on the determined first maximum number of MIMO layers andthe second maximum number of MIMO layers.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the disclosure will be more apparent from the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1A is a diagram illustrating a structure of a Long Term Evolution(LTE) system according to an embodiment of the disclosure;

FIG. 1B is a diagram illustrating a radio protocol architecture in anLTE system according to an embodiment of the disclosure;

FIG. 1C is a diagram illustrating a structure of a next-generationmobile communication system according to an embodiment of thedisclosure;

FIG. 1D is a diagram illustrating a radio protocol architecture of anext-generation mobile communication system according to an embodimentof the disclosure;

FIG. 1E is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure;

FIG. 1F is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure;

FIG. 1G is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure;

FIG. 1H is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure;

FIG. 1I is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure;

FIG. 1J is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure;

FIG. 1K is a diagram illustrating a method of signaling maxMIMO-Layerswhen a base station configures an uplink configuration (uplinkConfig)and an additional uplink configuration (supplementaryUplink) to a RadioResource Control (RRC) connection mode terminal for one serving cellaccording to an embodiment of the disclosure;

FIG. 1L is a diagram illustrating a structure of a terminal according toan embodiment of the disclosure;

FIG. 1M is a diagram illustrating a structure of a base stationaccording to an embodiment of the disclosure;

FIG. 1N is a diagram illustrating an example of wireless transmissionand reception paths according to an embodiment of the disclosure;

FIG. 1O is a diagram illustrating an example of wireless transmissionand reception paths according to an embodiment of the disclosure; and

FIG. 1P is a diagram illustrating an example embodiment for a bit-leveland a symbol-level processing of a terminal or a base station accordingto an embodiment of the disclosure.

Throughout the drawings, like reference numerals will be understood torefer to like parts, components, and structures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thedisclosure. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of thedisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of thedisclosure is provided for illustration purpose only and not for thepurpose of limiting the disclosure as defined by the appended claims andtheir equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

Throughout the disclosure, the expression “at least one of a, b or c”indicates only a, only b, only c, both a and b, both a and c, both b andc, all of a, b, and c, or variations thereof.

Examples of a terminal may include a user equipment (UE), a mobilestation (MS), a cellular phone, a smartphone, a computer, a multimediasystem capable of performing a communication function, and the like.

In the disclosure, a controller may also be referred to as a processor.

Throughout the specification, a layer (or a layer apparatus) may also bereferred to as an entity.

It will be understood that each block of process flowchart diagrams andcombinations of flowchart diagrams may be performed by computer programinstructions. Because these computer program instructions may be mountedon a processor of a general-purpose computer, special-purpose computer,or other programmable data processing equipment, the instructionsexecuted through a processor of a computer or other programmable dataprocessing equipment may generate a means of performing the functionsdescribed in the flowchart block(s). Because these computer programinstructions may be stored in a computer-usable or computer-readablememory that may be directed to a computer or other programmable dataprocessing equipment to implement a function in a particular manner, theinstructions stored in the computer-usable or computer-readable memorymay also produce a production item containing an instruction means ofperforming the functions described in the flowchart block(s). Becausethe computer program instructions may also be mounted on a computer orother programmable data processing equipment, the instructionsperforming a series of operations on the computer or other programmabledata processing equipment to generate a computer-implemented process toperform the computer or other programmable data processing equipment mayalso provide operations for executing the functions described in theflowchart block(s).

Also, each block may represent a portion of a module, segment, or codeincluding one or more executable instructions for executing one or morespecified logical functions. Also, it should be noted that the functionsmentioned in the blocks may also occur in a different order in somealternative implementation examples. For example, two blocks illustratedin succession may actually be performed substantially at the same timeor may sometimes be performed in the opposite order depending on thecorresponding function.

In this case, the term “˜unit” used in the embodiments may refer to asoftware component or a hardware component such as a field programmablegate array (FPGA) or an application specific integrated circuit (ASIC)and the “˜unit” may perform certain functions. However, the “˜unit” isnot limited to software or hardware. The “˜unit” may be configured to bein an addressable storage medium or may be configured to operate one ormore processors. Thus, as an example, the “˜unit” may include componentssuch as software components, object-oriented software components, classcomponents, and task components and may include processes, functions,attributes, procedures, subroutines, segments of program code, drivers,firmware, microcode, circuits, data, databases, data structures, tables,arrays, and variables. A function provided by the components and“˜units” may be associated with the smaller number of components and“˜units” or may be further divided into additional components and“˜units”. In addition, the components and “˜units” may be implemented tooperate one or more central processing units (CPUs) in a device or asecurity multimedia card. Also, in embodiments, the “˜unit” may includeone or more processors.

In the disclosure, a downlink (DL) may mean a wireless transmission pathof a signal transmitted from a base station to a terminal, and an uplink(UL) may mean a wireless transmission path of a signal transmitted froma terminal to a base station. Also, hereinafter, a Long Term Evolution(LTE) or LTE-A system may be described as an example; however,embodiments of the disclosure may also be applied to other communicationsystems having similar technical backgrounds or channel types. Forexample, 5th generation mobile communication technology (5G) (or NewRadio (NR)) developed after LTE-A may be included in systems to whichembodiments of the disclosure may be applied, and the following 5G maybe a concept including the existing LTE, LTE-A, and other similarservices. Also, the disclosure may also be applied to othercommunication systems through some modifications without departing fromthe scope of the disclosure by the judgment of those of ordinary skillin the art.

In the following description, terms for identifying access nodes, termsreferring to network entities, terms referring to messages, termsreferring to interfaces between network entities, terms referring tovarious identification information, and the like are used forconvenience of description. Thus, the disclosure is not limited to theterms described below and other terms referring to objects havingequivalent technical meanings may be used.

In the following description, terms and names defined in the 3^(rd)Generation Partnership Project Long Term Evolution (3GPP LTE) standardsmay be used for convenience of description. However, the disclosure isnot limited to those terms and names and may also be similarly appliedto systems according to other standards.

Hereinafter, a base station may be an agent performing terminal resourceallocation and may be at least one of a gNode B, an eNode B, a Node B, abase station (BS), a radio access unit, a base station controller, or anode on a network. Examples of a terminal may include a user equipment(UE), a mobile station (MS), a cellular phone, a smartphone, a computer,or a multimedia system capable of performing a communication function.However, the disclosure is not limited thereto.

Particularly, the disclosure may be applied to 3GPP NR (5G mobilecommunication standards). Also, the disclosure is applicable tointelligent services (e.g., smart home, smart building, smart city,smart car or connected car, health care, digital education, retail,security, and safety services) based on 5G communication technology andIoT technology. In the disclosure, eNB may be used mixed with gNB forconvenience of description. That is, a base station described as an eNBmay represent a gNB. Also, the term “terminal” may refer to otherwireless communication devices in addition to mobile phones, NB-IoTdevices, and sensors.

Wireless communication systems providing voice-based services are beingdeveloped to broadband wireless communication systems providinghigh-speed and high-quality packet data services according tocommunication standards such as high speed packet access (HSPA), longterm evolution (LTE) or evolved universal terrestrial radio access(E-UTRA), LTE-advanced (LTE-A), LTE-Pro of 3GPP, high rate packet data(HRPD) and ultra mobile broadband (UMB) of 3GPP2, and 802.16e of theInstitute of Electrical and Electronics Engineers (IEEE).

As a representative example of the broadband wireless communicationsystem, an LTE system uses Orthogonal Frequency Division Multiplexing(OFDM) in a downlink (DL) and uses Single Carrier-Frequency DivisionMultiple Access (SC-FDMA) in an uplink (UL). The uplink may refer to aradio link for transmitting data or a control signal from a terminal(e.g., a user equipment (UE) or a mobile station (MS)) to a base station(e.g., an eNode B (eNB) or a base station (BS)), and the downlink mayrefer to a radio link for transmitting data or a control signal from thebase station to the terminal. The above-described multiple accessschemes distinguish between data or control information of differentusers by allocating time-frequency resources for the data or controlinformation of the users not to overlap each other, that is, to achieveorthogonality therebetween.

As post-LTE systems, 5G systems may have to support services capable ofsimultaneously satisfying various requirements because they may have tofreely reflect various requirements of users, service providers, and thelike. Services considered for the 5G systems may include enhanced mobilebroadband (eMBB), massive machine-type communication (mMTC), andultra-reliability low-latency communication (URLLC) services.

According to an embodiment of the disclosure, the eMBB may aim toprovide an improved data rate than the data rate supported by theexisting LTE, LTE-A, or LTE-Pro. For example, in a 5G communicationsystem, the eMBB should be able to provide a peak data rate of 20 Gbpsin a downlink and a peak data rate of 10 Gbps in an uplink from theviewpoint of a base station. Also, the 5G communication system may haveto provide an increased user-perceived data rate of a terminal whileproviding a peak data rate. In order to satisfy this requirement, the 5Gcommunication system may require the improvement of varioustransmission/reception technologies including a more improved MultiInput Multi Output (MIMO) transmission technology. Also, the 5Gcommunication system may satisfy a required data rate by using afrequency bandwidth wider than 20 MHz in the 3 GHz to 6 GHz or 6 GHz ormore frequency band while transmitting signals by using a transmissionbandwidth of up to 20 MHz in the 2 GHz band used in the current LTE.

Simultaneously, the mMTC is being considered to support applicationservices such as Internet of Thing (IoT) in 5G communication systems. Inorder to efficiently provide the IoT, the mMTC may require the supportfor access of large terminals in a cell, improved terminal coverage,improved battery time, reduced terminal cost, and the like. Because theIoT is attached to various sensors and various devices to provide acommunication function, it should be able to support a large number ofterminals (e.g., 1,000,000 terminals/km²) in a cell. Also, because aterminal supporting the mMTC is likely to be located in a shadow areafailing to be covered by the cell, such as the basement of a building,due to the characteristics of the service, it may require wider coveragethan other services provided by the 5G communication systems. Theterminal supporting the mMTC should be configured as a low-cost terminaland may require a very long battery life time of about 10 years to about15 years because it is difficult to frequently replace the battery ofthe terminal.

Lastly, the URLLC may be used in services for remote control of robotsor machinery, industrial automation, unmanned aerial vehicles, remotehealth care, emergency alerts, and the like, as cellular-based wirelesscommunication services used for mission-critical purposes. Thus, thecommunication provided by the URLLC may have to provide very low latency(ultra-low latency) and very high reliability (ultra-high reliability).For example, a service supporting the URLLC should satisfy an airinterface latency of less than 0.5 milliseconds and simultaneously mayhave a requirement for a packet error rate of 10⁻⁵ or less. Thus, forthe service supporting the URLLC, the 5G system should provide a smallertransmit time interval (TTI) than other services and simultaneously mayhave a design requirement for allocating wide resources in frequencybands in order to secure the reliability of communication links.

The above three services of eMBB, URLLC, and mMTC considered in the 5Gcommunication systems may be multiplexed and transmitted in one system.In this case, different transmission/reception techniques andtransmission/reception parameters may be used between services in orderto satisfy different requirements of the respective services. However,the above-described mMTC, URLLC, and eMBB are merely examples ofdifferent service types, and the service types to which the disclosureis applied are not limited thereto.

Also, although embodiments of the disclosure will be described below byusing an LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobilecommunication) as an example, the embodiments of the disclosure may alsobe applied to other communication systems having similar technicalbackgrounds or channel types. Also, the embodiments of the disclosuremay also be applied to other communication systems through somemodifications without departing from the scope of the disclosure by thejudgment of those of ordinary skill in the art.

In the following description of the disclosure, detailed descriptions ofwell-known functions or configurations will be omitted because theywould unnecessarily obscure the subject matters of the disclosure.Hereinafter, embodiments of the disclosure will be described withreference to the accompanying drawings.

FIG. 1A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the disclosure.

Referring to FIG. 1A, a radio access network of the LTE system mayinclude next-generation base stations (e.g., evolved Node Bs (eNBs),Node Bs, or base stations) 1 a-05, 1 a-10, 1 a-15, and 1 a-20, amobility management entity (MME) 1 a-25, and a serving-gateway (S-GW) 1a-30. A user terminal (e.g., a user equipment (UE) or a terminal) 1 a-35may access an external network through the eNBs 1 a-05 to 1 a-20 and theS-GW 1 a-30.

In FIG. 1A, the eNBs 1 a-05 to 1 a-20 may correspond to the existingNode Bs of a Universal Mobile Telecommunication System (UMTS) system.The eNB may be connected to the UE 1 a-35 through a wireless channel andmay perform a more complex function than the existing Node B. In the LTEsystem, all user traffic including real-time services such as Voice overIP (VoIP) through the Internet protocol may be serviced on a sharedchannel Thus, a device for collecting and scheduling state informationsuch as the buffer states of UEs, available transmission power states,and channel states may be required, which may be performed by the ENBs 1a-05 to 1 a-20.

One eNB may generally control a plurality of cells. For example, inorder to implement a transmission rate of 100 Mbps, the LTE system mayuse Orthogonal Frequency Division Multiplexing (OFDM) as a radio accesstechnology in a 20 MHz bandwidth. Also, an adaptive modulation & coding(AMC) scheme may be applied to determine a modulation scheme and achannel coding rate according to the channel state of a terminal. TheS-GW 1 a-30 may be an apparatus for providing a data bearer and maygenerate or remove a data bearer under the control of the MME 1 a-25.The MME may be an apparatus for performing various control functions aswell as a mobility management function for a terminal and may beconnected to a plurality of base stations.

FIG. 1B is a diagram illustrating a radio protocol architecture in anLTE system according to an embodiment of the disclosure.

Referring to FIG. 1B, the radio protocol of the LTE system may include aPacket Data Convergence Protocol (PDCP) 1 b-05 and 1 b-40, a Radio LinkControl (RLC) 1 b-10 and 1 b-35, and a Medium Access Control (MAC) 1b-15 and 1 b-30 in each of a terminal and an eNB. The PDCP may performoperations such as IP header compression/decompression. The mainfunctions of the PDCP may be summarized as follows.

-   -   Header compression and decompression function (Header        compression and decompression: ROHC only)    -   User data transmission function (Transfer of user data)    -   Sequential transmission function (In-sequence delivery of upper        layer PDUs at PDCP re-establishment procedure for RLC AM)    -   Reordering function (For split bearers in DC (only support for        RLC AM): PDCP PDU routing for transmission and PDCP PDU        reordering for reception)    -   Duplicate detection function (Duplicate detection of lower layer        SDUs at PDCP re-establishment procedure for RLC AM)    -   Retransmission function (Retransmission of PDCP SDUs at handover        and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery        procedure, for RLC AM)    -   Ciphering and deciphering function (Ciphering and deciphering)    -   Timer-based SDU discard function (Timer-based SDU discard in        uplink)

The RLC 1 b-10 and 1 b-35 may reconfigure a PDCP packet data unit (PDU)in a suitable size to perform an ARQ operation and the like. The mainfunctions of the RLC may be summarized as follows.

-   -   Data transmission function (Transfer of upper layer PDUs)    -   ARQ function (Error Correction through ARQ (only for AM data        transfer))    -   Concatenation, segmentation, and reassembly function        (Concatenation, segmentation, and reassembly of RLC SDUs (only        for UM and AM data transfer))    -   Re-segmentation function (Re-segmentation of RLC data PDUs (only        for AM data transfer))    -   Reordering function (Reordering of RLC data PDUs (only for UM        and AM data transfer))    -   Duplicate detection function (Duplicate detection (only for UM        and AM data transfer))    -   Error detection function (Protocol error detection (only for AM        data transfer))    -   RLC SDU discard function (RLC SDU discard (only for UM and AM        data transfer))    -   RLC re-establishment function (RLC re-establishment)

The MAC 1 b-15 and 1 b-30 may be connected to several RLC layersconfigured in one terminal and may perform an operation of multiplexingRLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. Themain functions of the MAC may be summarized as follows.

-   -   Mapping function (Mapping between logical channels and transport        channels)    -   Multiplexing and demultiplexing function        (Multiplexing/demultiplexing of MAC SDUs belonging to one or        different logical channels into/from transport blocks (TB)        delivered to/from the physical layer on transport channels)    -   Scheduling information report function (Scheduling information        reporting)    -   HARQ function (Error correction through HARQ)    -   Priority handling function between logical channels (Priority        handling between logical channels of one UE)    -   Priority handling function between terminals (Priority handling        between UEs by means of dynamic scheduling)    -   MBMS service identification function (MBMS service        identification)    -   Transport format selection function (Transport format selection)    -   Padding function (Padding)

Physical layers 1 b-20 and 1 b-25 may channel-code and modulate upperlayer data, generate OFDM symbols, and transmit the same throughwireless channels or may demodulate and channel-decode OFDM symbolsreceived through wireless channels and transmit the result thereof tothe upper layer.

FIG. 1C is a diagram illustrating a structure of a next-generationmobile communication system according to an embodiment of thedisclosure.

Referring to FIG. 1C, a radio access network of the next-generationmobile communication system (hereinafter NR or 5G) may include anext-generation base station (New Radio Node B) (hereinafter NR gNB orNR base station) 1 c-10 and a next-generation radio core network (NewRadio Core (NR CN)) 1 c-05. A next-generation radio user terminal (NewRadio User Equipment (NR UE) or terminal) 1 c-15 may access an externalnetwork through the NR gNB 1 c-10 and the NR CN 1 c-05.

Referring again to FIG. 1C, the NR gNB 1 c-10 may correspond to anevolved Node B (eNB) of the existing LTE system. The NR gNB may beconnected to the NR UE 1 c-15 through a wireless channel and may providea better service than the existing Node B. In the next generation mobilecommunication system, all user traffic may be serviced on a sharedchannel Thus, a device for collecting and scheduling state informationsuch as the buffer states of UEs, available transmission power states,and channel states may be required, which may be performed by the NR gNB1 c-10. One NR gNB may generally control a plurality of cells. In thenext-generation mobile communication system, a bandwidth larger than orequal to the current maximum bandwidth may be applied to implementultra-high-speed data transmission compared to the current LTE. Also, abeamforming technology may be additionally combined by using OrthogonalFrequency Division Multiplexing (OFDM) as a radio access technology.Also, an adaptive modulation & coding (AMC) scheme may be applied todetermine a modulation scheme and a channel coding rate according to thechannel state of a terminal.

The NR CN 1 c-05 may perform functions such as mobility support, bearerconfiguration, and Quality of Service (QoS) configuration. The NR CN maybe an apparatus for performing various control functions as well as amobility management function for a terminal and may be connected to aplurality of base stations. Also, the next-generation mobilecommunication system may also be linked with the existing LTE system,and the NR CN may be connected to an MME 1 c-25 through a networkinterface. The MME may be connected to an eNB 1 c-30 that is an existingbase station.

FIG. 1D is a diagram illustrating a radio protocol architecture of anext-generation mobile communication system according to an embodimentof the disclosure.

Referring to FIG. 1D, the radio protocol of the next-generation mobilecommunication system may include NR Service Data Adaptation Protocol(SDAP) 1 d-01 and 1 d-45, NR PDCP 1 d-05 and 1 d-40, NR RLC 1 d-10 and 1d-35, NR MAC 1 d-15 and 1 d-30, and NR PHY 1 d-20 and 1 d-25 in each ofa terminal and an NR base station.

The main functions of the NR SDAP 1 d-01 and 1 d-45 may include some ofthe following functions.

-   -   User data transmission function (Transfer of user plane data)    -   Function of mapping between QoS flow and data bearer for uplink        and downlink (Mapping between a QoS flow and a DRB for both DL        and UL)    -   Function of marking QoS flow ID for uplink and downlink (Marking        QoS flow ID in both DL and UL packets)    -   Function of mapping reflective QoS flow to data bearer for        uplink SDAP PDUs (Reflective QoS flow to DRB mapping for the UL        SDAP PDUs)

As for an SDAP layer, the terminal may be configured with a RadioResource Control (RRC) message for each PDCP layer, for each bearer, orfor each logical channel whether to use a header of the SDAP layer orwhether to use a function of the SDAP layer. When an SDAP header isconfigured, the terminal may be indicated by a non-access stratum (NAS)Quality of Service (QoS) reflection configuration 1-bit indicator (NASreflective QoS) and an access stratum (AS) QoS reflection configuration1-bit indicator (AS reflective QoS) of the SDAP header to update orreconfigure mapping information between a data bearer and a QoS flow ofthe uplink and the downlink. The SDAP header may include QoS flow IDinformation representing the QoS. The QoS information may be used asdata processing priority and scheduling information or the like tosupport a smooth service.

The main functions of the NR PDCP 1 d-05 and 1 d-40 may include some ofthe following functions.

-   -   Header compression and decompression function (Header        compression and decompression: ROHC only)    -   User data transmission function (Transfer of user data)    -   Sequential transmission function (In-sequence delivery of upper        layer PDUs)    -   Non-sequential transmission function (Out-of-sequence delivery        of upper layer PDUs)    -   Reordering function (PDCP PDU reordering for reception)    -   Duplicate detection function (Duplicate detection of lower layer        SDUs)    -   Retransmission function (Retransmission of PDCP SDUs)    -   Ciphering and deciphering function (Ciphering and deciphering)    -   Timer-based SDU discard function (Timer-based SDU discard in        uplink)

In the above, the reordering function of the NR PDCP entity may mean afunction of reordering the PDCP PDUs received from the lower layer inorder based on a PDCP sequence number (SN). The reordering function ofthe NR PDCP entity may include a function of transmitting data to theupper layer in the reordered order, may include a function of directlytransmitting data without considering the order, may include a functionof rearranging the order and recording the missing PDCP PDUs, mayinclude a function of reporting the state of the missing PDCP PDUs tothe transmitting side, and may include a function of requestingretransmission of the missing PDCP PDUs.

The main functions of the NR RLC 1 d-10 and 1 d-35 may include some ofthe following functions.

-   -   Data transmission function (Transfer of upper layer PDUs)    -   Sequential transmission function (In-sequence delivery of upper        layer PDUs)    -   Non-sequential transmission function (Out-of-sequence delivery        of upper layer PDUs)    -   ARQ function (Error correction through ARQ)    -   Concatenation, segmentation, and reassembly function        (Concatenation, segmentation, and reassembly of RLC SDUs)    -   Re-segmentation function (Re-segmentation of RLC data PDUs)    -   Reordering function (Reordering of RLC data PDUs)    -   Duplicate detection function (Duplicate detection)    -   Error detection function (Protocol error detection)    -   RLC SDU discard function (RLC SDU discard)    -   RLC re-establishment function (RLC re-establishment)

In the above, the sequential transmission (in-sequence delivery)function of the NR RLC entity may mean a function of sequentiallytransmitting the RLC SDUs received from the lower layer to the upperlayer. When one original RLC SDU is divided into multiple RLC SDUs andthen received, the sequential transmission (in-sequence delivery)function of the NR RLC entity may include a function of reassembling andthen transmitting the same.

The sequential transmission (in-sequence delivery) function of the NRRLC entity may include a function of rearranging the received RLC PDUsbased on the RLC sequence number (SN) or the sequence number (SN), mayinclude a function of rearranging the order and recording the missingRLC PDUs, may include a function of reporting the state of the missingRLC PDUs to the transmitting side, and may include a function ofrequesting retransmission of the missing RLC PDUs.

The sequential transmission (in-sequence delivery) function of the NRRLC (1 d-10 and 1 d-35) entity may include a function of sequentiallytransmitting, when there is a missing RLC SDU, only the RLC SDUs up tobefore the missing RLC SDU to the upper layer. Also, the sequentialtransmission (in-sequence delivery) function of the NR RLC entity mayinclude a function of sequentially transmitting all RLC SDUs receivedbefore the start of a timer to the upper layer, when a certain timer hasexpired even when there is a missing RLC SDU. Also, the sequentialtransmission (in-sequence delivery) function of the NR RLC entity mayinclude a function of sequentially transmitting all RLC SDUs received upto now to the upper layer, when a certain timer has expired even whenthere is a missing RLC SDU.

The NR RLC (1 d-10 and 1 d-35) entity may process RLC PDUs in the orderof receiving the RLC PDUs regardless of the order of the sequence number(out of sequence delivery) and transmit the results thereof to the NRPDCP (1 d-05 and 1 d-40) entity.

In the case of receiving segments, the NR RLC (1 d-10 and 1 d-35) entitymay receive segments stored in a buffer or to be received afterward,reconfigure the segments into a single RLC PDU, and then transmit thesame to the NR PDCP entity.

The NR RLC layer may not include the concatenation function, and thisfunction may be performed in the NR MAC layer or may be replaced withthe multiplexing function of the NR MAC layer.

In the above, the non-sequential transmission (out-of-sequence delivery)function of the NR RLC entity may mean a function of directlytransmitting the RLC SDUs received from the lower layer to the upperlayer regardless of the order thereof. When one original RLC SDU isdivided into multiple RLC SDUs and then received, the non-sequentialtransmission (out-of-sequence delivery) function of the NR RLC entitymay include a function of reassembling and then transmitting the same.The non-sequential transmission (out-of-sequence delivery) function ofthe NR RLC entity may include a function of storing the RLC SN or PDCPSN of the received RLC PDUs, arranging the order thereof, and recordingthe missing RLC PDUs.

The NR MAC 1 d-15 and 1 d-30 may be connected to multiple NR RLCentities configured in one terminal, and the main functions of the NRMAC may include some of the following functions.

-   -   Mapping function (Mapping between logical channels and transport        channels)    -   Multiplexing and demultiplexing function        (Multiplexing/demultiplexing of MAC SDUs)    -   Scheduling information report function (Scheduling information        reporting)    -   HARQ function (Error correction through HARQ)    -   Priority handling function between logical channels (Priority        handling between logical channels of one UE)    -   Priority handling function between terminals (Priority handling        between UEs by means of dynamic scheduling)    -   MBMS service identification function (MBMS service        identification)    -   Transport format selection function (Transport format selection)    -   Padding function (Padding)

The NR PHY layers (1 b-20 and 1 b-25) may channel-code and modulateupper layer data, generate OFDM symbols, and transmit the same throughwireless channels or may demodulate and channel-decode OFDM symbolsreceived through wireless channels and transmit the result thereof tothe upper layer.

FIG. 1E is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell, according to an embodiment of thedisclosure. According to various embodiments of the disclosure, at leastone of the following operations may be omitted or modified in order toimplement embodiments of the disclosure.

Referring to FIG. 1E, the terminal may be in an RRC idle mode or an RRCinactive mode (operation 1 e-01).

In operation 1 e-05, the terminal in the RRC idle mode or the RRCinactive mode may establish an RRC connection with the base station whendata to be transmitted/received occurs. The terminal in the RRC idlemode may establish an RRC connection with the base station by performingan RRC connection establishment process with the base station. Also, theterminal in the RRC inactive mode may establish an RRC connection withthe base station by performing an RRC connection resume process with thebase station.

In operation 1 e-10, the terminal in an RRC connection mode may transmitcapability information of the terminal to the base station. According toan embodiment of the disclosure, the base station may request thecapability information of the terminal (UE radio access capabilityinformation) from the terminal in the RRC connection mode, and theterminal in the RRC connection mode may transmit the capabilityinformation of the terminal to the base station.

According to an embodiment of the disclosure, the base station maytransmit a UECapabilityEnquiry message (a terminal capabilityinformation request message) to the terminal. The UECapabilityEnquirymessage may include one or more UE-CapabilityRAT-RequestLists that areterminal capability request lists for a RAT. TheUE-CapabilityRAT-ReqeustList may include a capability request filter(capabilityRequestFilter) for each RAT type. Alternatively, theUECapabilityEnquiry message may include aUE-CapabilityRequestFilterCommon for requesting a terminal capabilityfiltered in common for all capability containers.

According to an embodiment of the disclosure, the terminal in the RRCconnection mode may transmit a terminal capability information message(a UECapabilityInformation message) to the base station based on theUECapabilityEnquiry message received from the base station. TheUECapabilityInformation message may include a terminal capabilitycontainer (a ue-CapabilityRAT-Container) for each RAT for one or moreRATs. For example, the terminal capability container for each RAT mayinclude a UE-NR-Capability including terminal radio access capabilityparameters for NR, and the UE-NR-Capability may include aFeatureSetUplink for the uplink (it is used to indicate the featuresthat the UE supports on the carriers corresponding to one band entry ina band combination). The FeatureSetUplink may include a MIMO-LayersULfor each component carrier or serving cell, that is, for eachFeatureSetUplinkPerCC.

In operation 1 e-15, the terminal may perform an RRC connectionreconfiguration process with the base station. The base station mayperform an RRC connection reconfiguration process (RRC reconfiguration)with the terminal for normal uplink configuration. The base station maytransmit an RRC connection reconfiguration message (anRRCReconfiguration message) to the terminal. The RRC connectionreconfiguration message may include configuration information for atleast one UL uplink band width part (BWP) for the uplink of one servingcell. For example, UplinkConfig may be included in uplinkConfig includedin ServingCellConfig IE, and at least one UL BWP may be configured inthe uplink of one serving cell. Also, maxRank may be configured for eachUL BWP (maxRank in PUSCH-Config in BWP-UplinkDedicated in uplinkConfigin ServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for the uplink of one serving cell(maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig inServingCellConfig). Upon receiving the RRC connection reconfigurationmessage, the terminal may apply the configuration information includedin the RRC connection reconfiguration message.

In operation 1 e-20, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). The maximum number of layers may be determined through thefollowing method.

-   -   When maxMIMO-Layers are configured for the serving cell        (maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig in        ServingCellConfig), the terminal may apply the maxMIMO-Layers        configured for all UL BWPs of the serving cell as the maximum        number of layers.    -   When maxMIMO-Layers are not configured for the serving cell and        maxRank is configured for one or more UL BWPs, the terminal may        apply the greatest maxRank for all UL BWPs of the serving cell        (the maximum value of maxRank across all UL BWPs of the serving        cell) as the maximum number of layers.    -   When maxMIMO-Layers and maxRank are not configured for the        serving cell, the terminal may apply the maximum number of        layers supported by the terminal for the serving cell for a        PUSCH transmission operation as the maximum number of layers.

In operation 1 e-25, the terminal may perform a physical uplink sharedchannel (PUSCH) transmission operation. For example, the terminal mayperform a PUSCH transmission operation by determining a rate matchingand a transport block size (TBS) size for PUSCH transmission in the ULBWP by applying the maximum number of layers determined in operation 1e-20.

According to an embodiment of the disclosure, when performing a limitedbuffer rate matching (LBRM), which limits the number of parity bits thatmay be transmitted among all parity bits generated by low density paritycheck (LDPC) coding for a particular input, the terminal may determinethe TBS size by performing a rate matching by applying the determinedmaximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performinga full buffer rate matching (FBRM) for transmitting all parity bitsgenerated by LDPC coding for a particular input, the terminal maydetermine the TBS size by performing a rate matching based on the numberof layers configured for each BWP for the serving cell.

In operation 1 e-30, the terminal may perform an RRC connectionreconfiguration process (RRC reconfiguration) with the base station toconfigure a supplementary uplink. The base station may transmit an RRCconnection reconfiguration message (an RRCReconfiguration message) tothe terminal. The RRC connection reconfiguration message may includeconfiguration information about a plurality of UL BWPs for asupplementary uplink of one serving cell. For example, UplinkConfig maybe included in supplementaryUplink included in ServingCellConfig IE, anda plurality of UL BWPs may be configured in a supplementary uplink ofone serving cell. Also, maxRank may be configured for each UL BWP(maxRank in PUSCH-Config in BWP-UplinkDedicated in supplementaryUplinkin ServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for a supplementary uplink of oneserving cell (maxMIMO-Layers in PUSCH-ServingCellConfig insupplementaryUplink in ServingCellConfig). Upon receiving the RRCconnection reconfiguration message, the terminal may apply theconfiguration information included in the RRC connection reconfigurationmessage.

In operation 1 e-35, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). The maximum number of layers may be determined by applying atleast one of the following methods.

-   -   According to an embodiment of the disclosure, when both        maxMIMO-Layers of uplinkConfig and maxMIMO-Layers of        supplementaryUplink are configured for the serving cell and the        two maxMIMO-Layers values are equal to each other, the terminal        may apply the MaxMIMO-Layers configured for all UL BWPs of the        serving cell as the maximum number of layers (operation 1 e-45).

In operation 1 e-60, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers values applied in operation 1e-45. For example, the terminal may determine a rate matching and a TBSsize for PUSCH transmission in the UL BWP by applying the determinedmaximum number of layers and perform a PUSCH transmission operation.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

-   -   According to an embodiment of the disclosure, when both        maxMIMO-Layers of uplinkConfig and maxMIMO-Layers of        supplementaryUplink are configured for the serving cell and the        two maxMIMO-Layers values are different from each other, the        terminal may perform an RRC connection re-establishment process        with the base station (operation 1 e-40).

For example, because the terminal may determine that the maxMIMO-Layersused in the uplink and the maxMIMO-Layers used in the supplementaryuplink are always configured as the same value for one serving cell, theterminal may determine that this may not be applied when themaxMIMO-Layers of the uplink and the supplementary are different values(UE is unable to comply with (part of) the configuration included in theRRCReconfiguration message) and may perform an RRC connectionre-establishment process with the base station.

-   -   According to an embodiment of the disclosure, when only the        maxMIMO-Layers value of uplinkConfig is configured or only the        maxMIMO-Layers value of supplementaryUplink is configured for        the serving cell, the terminal may apply the maxMIMO-Layers        value signaled for all UL BWPs of the serving cell as the        maximum number of layers (operation 1 e-45).

Also, in operation 1 e-60, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers values applied in operation 1e-45. For example, the terminal may determine a rate matching and a TBSsize for PUSCH transmission in the UL BWP by applying the determinedmaximum number of layers and perform a PUSCH transmission operation.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan LBRM, which limits the number of parity bits that may be transmittedamong all parity bits generated by LDPC coding for a particular input,the terminal may determine the size of the buffer of the LBRM byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

-   -   According to an embodiment of the disclosure, when both the        maxMIMO-Layers of uplinkConfig and the maxMIMO-Layers of        supplementaryUplink are not configured for the serving cell and        maxRank is configured for one or more UL BWPs for the uplink or        max is configured for one or more UL BWPs for the supplementary        uplink (maxRank is signaled/configured in uplinkConfig and/or        supplementaryUplink), the terminal may apply the greatest        maxRank for all UL BWPs of the serving cell (the maximum value        of maxRank across all UL BWPs of the serving cell) as the        maximum number of layers (operation 1 e-50).

Also, in operation 1 e-60, the terminal may perform a PUSCH transmissionoperation based on the maximum number of layers determined in operation1 e-50. For example, the terminal may perform a PUSCH transmissionoperation by determining a rate matching and a TBS size for PUSCHtransmission in the UL BWP by applying the determined maximum number oflayers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

-   -   According to an embodiment of the disclosure, when the        maxMIMO-Layers and the maxRank are not configured for the        serving cell, the terminal may apply the maximum number of        layers supported by the terminal for the serving cell (operation        1 e-55).

Also, in operation 1 e-60, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers values applied in operation 1e-55. For example, the terminal may perform a PUSCH transmissionoperation by determining a rate matching and a TBS size for PUSCHtransmission in the UL BWP by applying the determined maximum number oflayers.

According to an embodiment of the disclosure, in the case of performingan LBRM, which limits the number of parity bits that may be transmittedamong all parity bits generated by LDPC coding for a particular input,the terminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan LBRM, which limits the number of parity bits that may be transmittedamong all parity bits generated by LDPC coding for a particular input,the terminal may determine the size of the buffer of the LBRM byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, in the case of an FBRM fortransmitting all parity bits generated by LDPC coding for a particularinput, the terminal may determine the TBS size by performing a ratematching based on the number of layers configured for each BWP for theserving cell.

FIG. 1F is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell, according to an embodiment of thedisclosure. According to various embodiments of the disclosure, at leastone of the following operations may be omitted or modified in order toimplement embodiments of the disclosure.

Referring to FIG. 1F, the terminal may be in an RRC idle mode or an RRCinactive mode (operation 1 f-01).

In operation 1 f-05, the terminal in the RRC idle mode or the RRCinactive mode may establish an RRC connection with the base station whendata to be transmitted/received occurs afterward. The terminal in theRRC idle mode may establish an RRC connection with the base station byperforming an RRC connection establishment process with the basestation. Also, the terminal in the RRC inactive mode may establish anRRC connection with the base station by performing an RRC connectionresume process with the base station.

In operation 1 f-10, the terminal in an RRC connection mode may transmitcapability information of the terminal to the base station. According toan embodiment of the disclosure, the base station may request thecapability information of the terminal (UE radio access capabilityinformation) from the terminal in the RRC connection mode, and theterminal in the RRC connection mode may transmit the capabilityinformation of the terminal to the base station.

According to an embodiment of the disclosure, the base station maytransmit a UECapabilityEnquiry message (a terminal capabilityinformation request message) to the terminal. The UECapabilityEnquirymessage may include one or more UE-CapabilityRAT-RequestLists that areterminal capability request lists for a RAT. TheUE-CapabilityRAT-ReqeustList may include a capability request filter(capabilityRequestFilter) for each RAT type. Alternatively, theUECapabilityEnquiry message may include aUE-CapabilityRequestFilterCommon for requesting a terminal capabilityfiltered in common for all capability containers.

According to an embodiment of the disclosure, the terminal in the RRCconnection mode may transmit a terminal capability information message(a UECapabilityInformation message) to the base station based on theUECapabilityEnquiry message received from the base station. TheUECapabilityInformation message may include a terminal capabilitycontainer (a UE-CapabilityRAT-Container) for each RAT for one or moreRATs. For example, the terminal capability container for each RAT mayinclude a UE-NR-Capability including terminal radio access capabilityparameters for NR, and the UE-NR-Capability may include aFeatureSetUplink for the uplink (it is used to indicate the featuresthat the UE supports on the carriers corresponding to one band entry ina band combination). The FeatureSetUplink may include a MIMO-LayersULfor each component carrier or serving cell, that is, for eachFeatureSetUplinkPerCC.

In operation 1 f-15, the terminal may perform an RRC connectionreconfiguration process with the base station. The base station mayperform an RRC connection reconfiguration process (RRC reconfiguration)with the terminal for normal uplink configuration. The base station maytransmit an RRC connection reconfiguration message (anRRCReconfiguration message) to the terminal. The RRC connectionreconfiguration message may include configuration information about atleast one UL BWP for an uplink of one serving cell. For example,UplinkConfig may be included in uplinkConfig included inServingCellConfig IE, and at least one UL BWP may be configured in theuplink of one serving cell. Also, maxRank may be configured for each ULBWP (maxRank in PUSCH-Config in BWP-UplinkDedicated in uplinkConfig inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for an uplink of one serving cell(maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig inServingCellConfig). Upon receiving the RRC connection reconfigurationmessage, the terminal may apply the configuration information includedin the RRC connection reconfiguration message.

In operation 1 f-20, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). The maximum number of layers may be determined through thefollowing method.

-   -   When maxMIMO-Layers are configured for the serving cell        (maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig in        ServingCellConfig), the terminal may apply the maxMIMO-Layers        configured for all UL BWPs of the serving cell as the maximum        number of layers.    -   When maxMIMO-Layers are not configured for the serving cell and        maxRank is configured for one or more UL BWPs, the terminal may        apply the greatest maxRank for all UL BWPs of the serving cell        (the maximum value of maxRank across all UL BWPs of the serving        cell) as the maximum number of layers.    -   When maxMIMO-Layers and maxRank are not configured for the        serving cell, the terminal may apply the maximum number of        layers supported by the terminal for the serving cell for a        PUSCH transmission operation as the maximum number of layers.

In operation 1 f-25, the terminal may perform a PUSCH transmissionoperation. For example, the terminal may perform a PUSCH transmissionoperation by determining a rate matching and a TBS size for PUSCHtransmission in the UL BWP by applying the maximum number of layersdetermined in operation 1 f-20.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

In operation 1 f-30, the terminal may perform an RRC connectionreconfiguration process (RRC reconfiguration) with the base station toconfigure a supplementary uplink. The base station may transmit an RRCconnection reconfiguration message (an RRCReconfiguration message) tothe terminal. The RRC connection reconfiguration message may includeconfiguration information about at least one UL BWP for a supplementaryuplink of one serving cell. For example, UplinkConfig may be included insupplementaryUplink included in ServingCellConfig 1E, and at least oneUL BWP may be configured in the supplementary uplink of one servingcell. Also, maxRank may be configured for each UL BWP (maxRank inPUSCH-Config in BWP-UplinkDedicated in supplementaryUplink inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for a supplementary uplink of oneserving cell (maxMIMO-Layers in PUSCH-ServingCellConfig insupplementaryUplink in ServingCellConfig). Upon receiving the RRCconnection reconfiguration message, the terminal may apply theconfiguration information included in the RRC connection reconfigurationmessage.

In operation 1 f-35, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). According to various embodiments of the disclosure, themaximum number of layers may be determined through at least one of thefollowing methods.

-   -   According to an embodiment of the disclosure, when both the        maxMIMO-Layers of uplinkConfig and the maxMIMO-Layers of        supplementaryUplink are configured for the serving cell and the        two maxMIMO-Layers values are different from each other, the        terminal may determine that the maxMIMO-Layers used in the        uplink and the maxMIMO-Layers used in the supplementary uplink        are always configured as the same value. Thus, the terminal may        apply the most recently signaled maxMIMO-Layers value for all        BWPs of the serving cell as the maximum number of layers. This        may be because the most recently signaled maxMIMO-Layers value        may best reflect at least one of the current channel state or        the terminal state.

In operation 1 f-45, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers value applied in operation 1 f-40.For example, the terminal may perform a PUSCH transmission operation bydetermining a rate matching and a TBS size for PUSCH transmission in theUL BWP by applying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

FIG. 1G is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure. According to various embodiments of the disclosure, at leastone of the following operations may be omitted or modified in order toimplement embodiments of the disclosure.

Referring to FIG. 1G, the terminal may be in an RRC idle mode or an RRCinactive mode (operation 1 g-01).

In operation 1 g-05, the terminal in the RRC idle mode or the RRCinactive mode may establish an RRC connection with the base station whendata to be transmitted/received occurs afterward. The terminal in theRRC idle mode may establish an RRC connection with the base station byperforming an RRC connection establishment process with the basestation. Also, the terminal in the RRC inactive mode may establish anRRC connection with the base station by performing an RRC connectionresume process with the base station.

In operation 1 g-10, the terminal in an RRC connection mode may transmitcapability information of the terminal to the base station. According toan embodiment of the disclosure, the base station may request thecapability information of the terminal (UE radio access capabilityinformation) from the terminal in the RRC connection mode, and theterminal in the RRC connection mode may transmit the capabilityinformation of the terminal to the base station.

According to an embodiment of the disclosure, the base station maytransmit a UECapabilityEnquiry message (a terminal capabilityinformation request message) to the terminal. The UECapabilityEnquirymessage may include one or more UE-CapabilityRAT-RequestLists that areterminal capability request lists for RAT. TheUE-CapabilityRAT-ReqeustList may include a capability request filter(capabilityRequestFilter) for each RAT type. Alternatively, theUECapabilityEnquiry message may include aUE-CapabilityRequestFilterCommon for requesting a terminal capabilityfiltered in common for all capability containers.

According to an embodiment of the disclosure, the terminal in the RRCconnection mode may transmit a terminal capability information message(a UECapabilityInformation message) to the base station based on theUECapabilityEnquiry message received from the base station. TheUECapabilityInformation message may include a terminal capabilitycontainer (a UE-CapabilityRAT-Container) for each RAT for one or moreRATs. For example, the terminal capability container for each RAT mayinclude a UE-NR-Capability including terminal radio access capabilityparameters for NR, and the UE-NR-Capability may include aFeatureSetUplink for the uplink (it is used to indicate the featuresthat the UE supports on the carriers corresponding to one band entry ina band combination). The FeatureSetUplink may include a MIMO-LayersULfor each component carrier or serving cell, that is, for eachFeatureSetUplinkPerCC.

In operation 1 g-15, the terminal may perform an RRC connectionreconfiguration process with the base station. The base station mayperform an RRC connection reconfiguration process (RRC reconfiguration)with the terminal for normal uplink configuration. The base station maytransmit an RRC connection reconfiguration message (anRRCReconfiguration message) to the terminal. The RRC connectionreconfiguration message may include configuration information about atleast one UL BWP for an uplink of one serving cell. For example,UplinkConfig may be included in uplinkConfig included inServingCellConfig IE, and at least one UL BWP may be configured in theuplink of one serving cell. Also, maxRank may be configured for each ULBWP (maxRank in PUSCH-Config in BWP-UplinkDedicated in uplinkConfig inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for an uplink of one serving cell(maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig inServingCellConfig). Upon receiving the RRC connection reconfigurationmessage, the terminal may apply the configuration information includedin the RRC connection reconfiguration message.

In operation 1 g-20, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). The maximum number of layers may be determined through thefollowing method.

-   -   When maxMIMO-Layers are configured for the serving cell        (maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig in        ServingCellConfig), the terminal may apply the maxMIMO-Layers        configured for all UL BWPs of the serving cell as the maximum        number of layers.    -   When maxMIMO-Layers are not configured for the serving cell and        maxRank is configured for one or more UL BWPs, the terminal may        apply the greatest maxRank for all UL BWPs of the serving cell        (the maximum value of maxRank across all UL BWPs of the serving        cell) as the maximum number of layers.    -   When maxMIMO-Layers and maxRank are not configured for the        serving cell, the terminal may apply the maximum number of        layers supported by the terminal for the serving cell for a        PUSCH transmission operation as the maximum number of layers.

In operation 1 g-25, the terminal may perform a PUSCH transmissionoperation. For example, the terminal may perform a PUSCH transmissionoperation by determining a rate matching and a TBS size for PUSCHtransmission in the UL BWP by applying the maximum number of layersdetermined in operation 1 g-20.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

In operation 1 g-30, the terminal may perform an RRC connectionreconfiguration process (RRC reconfiguration) with the base station toconfigure a supplementary uplink. The base station may transmit an RRCconnection reconfiguration message (an RRCReconfiguration message) tothe terminal. The RRC connection reconfiguration message may includeconfiguration information about at least one UL BWP for a supplementaryuplink of one serving cell. For example, UplinkConfig may be included insupplementaryUplink included in ServingCellConfig 1E, and at least oneUL BWP may be configured in the supplementary uplink of one servingcell. Also, maxRank may be configured for each UL BWP (maxRank inPUSCH-Config in BWP-UplinkDedicated in supplementaryUplink inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for a supplementary uplink of oneserving cell (maxMIMO-Layers in PUSCH-ServingCellConfig insupplementaryUplink in ServingCellConfig). Upon receiving the RRCconnection reconfiguration message, the terminal may apply theconfiguration information included in the RRC connection reconfigurationmessage.

In operation 1 g-35, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). According to various embodiments of the disclosure, themaximum number of layers may be determined through the following method.

-   -   According to an embodiment of the disclosure, when both the        maxMIMO-Layers of uplinkConfig and the maxMIMO-Layers of        supplementaryUplink are configured for the serving cell and the        two maxMIMO-Layers values are different from each other, the        terminal may apply the maxMIMO-Layers value signaled in the        uplinkConfig for all UL BWPs for the (normal) uplink of the        serving cell as the maximum number of layers and apply the        maxMIMO-layers value signaled in the supplementaryUplink for all        UL BWPs for the supplementary uplink of the serving cell (1 g-40        operation).

The (normal) uplink and the supplementary uplink may operate indifferent frequency bands and the MIMO performance thereof may differdepending on the frequency band thereof. The terminal may transmitinformation about the different MIMO performances to the base station inUE-NR-Capability. The base station (gNB) may configure themaxMIMO-Layers value differently for the (normal) uplink and thesupplementary uplink of the terminal based on the received capabilityinformation.

In operation 1 g-45, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers values respectively applied to theuplink and the supplementary uplink in operation 1 g-40. For example,the terminal may determine a rate matching and a TBS size for PUSCHtransmission in the UL BWP configured for the (normal) uplink byapplying the maximum number of layers determined for the uplink of theserving cell (maxMIMO-Layers in uplinkConfig). The terminal may performa PUSCH transmission operation based on the determined rate matching andTBS size.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the uplink of the serving cell.

According to an embodiment of the disclosure, the terminal may determinea rate matching and a TBS size for PUSCH transmission in the UL BWPconfigured for the supplementary uplink by applying the maximum numberof layers determined for the supplementary uplink of the serving cell(maxMIMO-Layers in supplementaryUplink). The terminal may perform aPUSCH transmission operation based on the determined rate matching andTBS size.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the supplementary uplink of the serving cell.

FIG. 1H is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure. According to various embodiments of the disclosure, at leastone of the following operations may be omitted or modified in order toimplement embodiments of the disclosure.

Referring to FIG. 1H, the terminal may be in an RRC idle mode or an RRCinactive mode (operation 1 h-01).

In operation 1 h-05, the terminal in the RRC idle mode or the RRCinactive mode may establish an RRC connection with the base station whendata to be transmitted/received occurs afterward. The terminal in theRRC idle mode may establish an RRC connection with the base station byperforming an RRC connection establishment process with the basestation. Also, the terminal in the RRC inactive mode may establish anRRC connection with the base station by performing an RRC connectionresume process with the base station.

In operation 1 h-10, the terminal in an RRC connection mode may transmitcapability information of the terminal to the base station. According toan embodiment of the disclosure, the base station may request thecapability information of the terminal (UE radio access capabilityinformation) from the terminal in the RRC connection mode, and theterminal in the RRC connection mode may transmit the capabilityinformation of the terminal to the base station.

According to an embodiment of the disclosure, the base station maytransmit a UECapabilityEnquiry message (a terminal capabilityinformation request message) to the terminal. The UECapabilityEnquirymessage may include one or more UE-CapabilityRAT-RequestLists that areterminal capability request lists for RAT. TheUE-CapabilityRAT-ReqeustList may include a capability request filter(capabilityRequestFilter) for each RAT type. Alternatively, theUECapabilityEnquiry message may include aUE-CapabilityRequestFilterCommon for requesting a terminal capabilityfiltered in common for all capability containers.

According to an embodiment of the disclosure, the terminal in the RRCconnection mode may transmit a terminal capability information message(a UECapabilityInformation message) to the base station based on theUECapabilityEnquiry message received from the base station. TheUECapabilityInformation message may include a terminal capabilitycontainer (a UE-CapabilityRAT-Container) for each RAT for one or moreRATs. For example, the terminal capability container for each RAT mayinclude a UE-NR-Capability including terminal radio access capabilityparameters for NR, and the UE-NR-Capability may include aFeatureSetUplink for the uplink (it is used to indicate the featuresthat the UE supports on the carriers corresponding to one band entry ina band combination). The FeatureSetUplink may include a MIMO-LayersULfor each component carrier or serving cell, that is, for eachFeatureSetUplinkPerCC.

In operation 1 h-15, the terminal may perform an RRC connectionreconfiguration process with the base station. The base station mayperform an RRC connection reconfiguration process (RRC reconfiguration)with the terminal for normal uplink configuration. The base station maytransmit an RRC connection reconfiguration message (anRRCReconfiguration message) to the terminal. The RRC connectionreconfiguration message may include configuration information about atleast one UL BWP for an uplink of one serving cell. For example,UplinkConfig may be included in uplinkConfig included inServingCellConfig IE, and at least one UL BWP may be configured in theuplink of one serving cell. Also, maxRank may be configured for each ULBWP (maxRank in PUSCH-Config in BWP-UplinkDedicated in uplinkConfig inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for an uplink of one serving cell(maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig inServingCellConfig). Upon receiving the RRC connection reconfigurationmessage, the terminal may apply the configuration information includedin the RRC connection reconfiguration message.

In operation 1 h-20, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). The maximum number of layers may be determined through thefollowing method.

-   -   When maxMIMO-Layers are configured for the serving cell        (maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig in        ServingCellConfig), the terminal may apply the maxMIMO-Layers        configured for all UL BWPs of the serving cell as the maximum        number of layers.    -   When maxMIMO-Layers are not configured for the serving cell and        maxRank is configured for one or more UL BWPs, the terminal may        apply the greatest maxRank for all UL BWPs of the serving cell        (the maximum value of maxRank across all UL BWPs of the serving        cell) as the maximum number of layers.    -   When maxMIMO-Layers and maxRank are not configured for the        serving cell, the terminal may apply the maximum number of        layers supported by the terminal for the serving cell for a        PUSCH transmission operation as the maximum number of layers.

In operation 1 h-25, the terminal may perform a PUSCH transmissionoperation. For example, the terminal may perform a PUSCH transmissionoperation by determining a rate matching and a TBS size for PUSCHtransmission in the UL BWP by applying the maximum number of layersdetermined in operation 1 h-20.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

In operation 1 h-30, the terminal may perform an RRC connectionreconfiguration process (RRC reconfiguration) with the base station toconfigure a supplementary uplink. The base station may transmit an RRCconnection reconfiguration message (an RRCReconfiguration message) tothe terminal. The RRC connection reconfiguration message may includeconfiguration information about at least one UL BWP for a supplementaryuplink of one serving cell. For example, UplinkConfig may be included insupplementaryUplink included in ServingCellConfig 1E, and at least oneUL BWP may be configured in the supplementary uplink of one servingcell. Also, maxRank may be configured for each UL BWP (maxRank inPUSCH-Config in BWP-UplinkDedicated in supplementaryUplink inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for a supplementary uplink of oneserving cell (maxMIMO-Layers in PUSCH-ServingCellConfig insupplementaryUplink in ServingCellConfig). Upon receiving the RRCconnection reconfiguration message, the terminal may apply theconfiguration information included in the RRC connection reconfigurationmessage.

In operation 1 h-35, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). According to various embodiments of the disclosure, themaximum number of layers may be determined through the following method.

-   -   According to an embodiment of the disclosure, when both the        maxMIMO-Layers of uplinkConfig and the maxMIMO-Layers of        supplementaryUplink are configured for the serving cell and the        two maxMIMO-Layers values are different from each other, the        terminal may apply the greater value of the maxMIMO-Layers        signaled for all UL BWPs of the serving cell as the maximum        number of layers. When the greater value of maxMIMO-Layers is        applied, there may be an advantage in that the terminal may        transmit more data to the base station in one TB. The terminal        may apply the greatest value among the maxMIMO-Layers values        signaled for all UL BWPs of the serving cell as the maximum        number of layers (operation 1 h-40).

In operation 1 h-45, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers value applied in operation 1 h-40.For example, the terminal may determine a rate matching and a TBS sizefor PUSCH transmission in the UL BWP by applying the determined maximumnumber of layers. The terminal may perform a PUSCH transmissionoperation based on the determined rate matching and TBS size.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

FIG. 1I is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure. According to various embodiments of the disclosure, at leastone of the following operations may be omitted or modified in order toimplement embodiments of the disclosure.

Referring to FIG. 1I, the terminal may be in an RRC idle mode or an RRCinactive mode (operation 1 i-01).

In operation 1 i-05, the terminal in the RRC idle mode or the RRCinactive mode may establish an RRC connection with the base station whendata to be transmitted/received occurs afterward. The terminal in theRRC idle mode may establish an RRC connection with the base station byperforming an RRC connection establishment process with the basestation. Also, the terminal in the RRC inactive mode may establish anRRC connection with the base station by performing an RRC connectionresume process with the base station.

In operation 1 i-10, the terminal in an RRC connection mode may transmitcapability information of the terminal to the base station. According toan embodiment of the disclosure, the base station may request thecapability information of the terminal (UE radio access capabilityinformation) from the terminal in the RRC connection mode, and theterminal in the RRC connection mode may transmit the capabilityinformation of the terminal to the base station.

According to an embodiment of the disclosure, the base station maytransmit a UECapabilityEnquiry message (a terminal capabilityinformation request message) to the terminal. The UECapabilityEnquirymessage may include one or more UE-CapabilityRAT-RequestLists that areterminal capability request lists for RAT. TheUE-CapabilityRAT-ReqeustList may include a capability request filter(capabilityRequestFilter) for each RAT type. Alternatively, theUECapabilityEnquiry message may include aUE-CapabilityRequestFilterCommon for requesting a terminal capabilityfiltered in common for all capability containers.

According to an embodiment of the disclosure, the terminal in the RRCconnection mode may transmit a terminal capability information message(a UECapabilityInformation message) to the base station based on theUECapabilityEnquiry message received from the base station. TheUECapabilityInformation message may include a terminal capabilitycontainer (a UE-CapabilityRAT-Container) for each RAT for one or moreRATs. For example, the terminal capability container for each RAT mayinclude a UE-NR-Capability including terminal radio access capabilityparameters for NR, and the UE-NR-Capability may include aFeatureSetUplink for the uplink (it is used to indicate the featuresthat the UE supports on the carriers corresponding to one band entry ina band combination). The FeatureSetUplink may include a MIMO-LayersULfor each component carrier or serving cell, that is, for eachFeatureSetUplinkPerCC.

In operation 1 i-15, the terminal may perform an RRC connectionreconfiguration process with the base station. The base station mayperform an RRC connection reconfiguration process (RRC reconfiguration)with the terminal for normal uplink configuration. The base station maytransmit an RRC connection reconfiguration message (anRRCReconfiguration message) to the terminal. The RRC connectionreconfiguration message may include configuration information about atleast one UL BWP for an uplink of one serving cell. For example,UplinkConfig may be included in uplinkConfig included inServingCellConfig IE, and at least one UL BWP may be configured in theuplink of one serving cell. Also, maxRank may be configured for each ULBWP (maxRank in PUSCH-Config in BWP-UplinkDedicated in uplinkConfig inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for an uplink of one serving cell(maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig inServingCellConfig). Upon receiving the RRC connection reconfigurationmessage, the terminal may apply the configuration information includedin the RRC connection reconfiguration message.

In operation 1 i-20, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). The maximum number of layers may be determined through thefollowing method.

-   -   When maxMIMO-Layers are configured for the serving cell        (maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig in        ServingCellConfig), the terminal may apply the maxMIMO-Layers        configured for all UL BWPs of the serving cell as the maximum        number of layers.    -   When maxMIMO-Layers are not configured for the serving cell and        maxRank is configured for one or more UL BWPs, the terminal may        apply the greatest maxRank for all UL BWPs of the serving cell        (the maximum value of maxRank across all UL BWPs of the serving        cell) as the maximum number of layers.    -   When maxMIMO-Layers and maxRank are not configured for the        serving cell, the terminal may apply the maximum number of        layers supported by the terminal for the serving cell for a        PUSCH transmission operation as the maximum number of layers.

In operation 1 i-25, the terminal may perform a PUSCH transmissionoperation. For example, the terminal may perform a PUSCH transmissionoperation by determining a rate matching and a TBS size for PUSCHtransmission in the UL BWP by applying the maximum number of layersdetermined in operation 1 i-20.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

In operation 1 i-30, the terminal may perform an RRC connectionreconfiguration process (RRC reconfiguration) with the base station toconfigure a supplementary uplink. The base station may transmit an RRCconnection reconfiguration message (an RRCReconfiguration message) tothe terminal. The RRC connection reconfiguration message may includeconfiguration information about at least one UL BWP for a supplementaryuplink of one serving cell. For example, UplinkConfig may be included insupplementaryUplink included in ServingCellConfig IE, and at least oneUL BWP may be configured in the supplementary uplink of one servingcell. Also, maxRank may be configured for each UL BWP (maxRank inPUSCH-Config in BWP-UplinkDedicated in supplementaryUplink inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for a supplementary uplink of oneserving cell (maxMIMO-Layers in PUSCH-ServingCellConfig insupplementaryUplink in ServingCellConfig). Upon receiving the RRCconnection reconfiguration message, the terminal may apply theconfiguration information included in the RRC connection reconfigurationmessage.

In operation 1 i-35, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). According to various embodiments of the disclosure, themaximum number of layers may be determined through the following method.

-   -   According to an embodiment of the disclosure, when both the        maxMIMO-Layers of uplinkConfig and the maxMIMO-Layers of        supplementaryUplink are configured for the serving cell and the        two maxMIMO-Layers values are different from each other, the        terminal may apply the smaller value among the maxMIMO-Layers        values signaled for all UL BWPs of the serving cell as the        maximum number of layers. When the smaller value of        maxMIMO-Layers is applied, there may be an advantage of        increasing the resource efficiency of the terminal and the base        station. Also, a method of limiting the maximum number of layers        of the terminal may be used as a method of reducing the current        consumption. The terminal may apply the smallest value among the        maxMIMO-Layers values signaled for all UL BWPs of the serving        cell as the maximum number of layers (operation 1 i-40).

In operation 1 i-45, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers value applied in operation 1 i-40.For example, the terminal may determine a rate matching and a TBS sizefor PUSCH transmission in the UL BWP by applying the determined maximumnumber of layers. The terminal may perform a PUSCH transmissionoperation based on the determined rate matching and TBS size.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

FIG. 1J is a diagram illustrating a terminal operation for a case wherea terminal is configured with an uplink configuration (uplinkConfig) andan additional uplink configuration (supplementaryUplink) from a basestation for one serving cell according to an embodiment of thedisclosure. According to various embodiments of the disclosure, at leastone of the following operations may be omitted or modified in order toimplement embodiments of the disclosure.

Referring to FIG. 1J, the terminal may be in an RRC idle mode or an RRCinactive mode (operation 1 j-01).

In operation 1 j-05, the terminal in the RRC idle mode or the RRCinactive mode may establish an RRC connection with the base station whendata to be transmitted/received occurs afterward. The terminal in theRRC idle mode may establish an RRC connection with the base station byperforming an RRC connection establishment process with the basestation. Also, the terminal in the RRC inactive mode may establish anRRC connection with the base station by performing an RRC connectionresume process with the base station.

In operation 1 j-10, the terminal in an RRC connection mode may transmitcapability information of the terminal to the base station. According toan embodiment of the disclosure, the base station may request thecapability information of the terminal (UE radio access capabilityinformation) from the terminal in the RRC connection mode, and theterminal in the RRC connection mode may transmit the capabilityinformation of the terminal to the base station.

According to an embodiment of the disclosure, the base station maytransmit a UECapabilityEnquiry message (a terminal capabilityinformation request message) to the terminal. The UECapabilityEnquirymessage may include one or more UE-CapabilityRAT-RequestLists that areterminal capability request lists for RAT. TheUE-CapabilityRAT-ReqeustList may include a capability request filter(capabilityRequestFilter) for each RAT type. Alternatively, theUECapabilityEnquiry message may include aUE-CapabilityRequestFilterCommon for requesting a terminal capabilityfiltered in common for all capability containers.

According to an embodiment of the disclosure, the terminal in the RRCconnection mode may transmit a terminal capability information message(a UECapabilityInformation message) to the base station based on theUECapabilityEnquiry message received from the base station. TheUECapabilityInformation message may include a terminal capabilitycontainer (a UE-CapabilityRAT-Container) for each RAT for one or moreRATs. For example, the terminal capability container for each RAT mayinclude a UE-NR-Capability including terminal radio access capabilityparameters for NR, and the UE-NR-Capability may include aFeatureSetUplink for the uplink (it is used to indicate the featuresthat the UE supports on the carriers corresponding to one band entry ina band combination). The FeatureSetUplink may include a MIMO-LayersULfor each component carrier or serving cell, that is, for eachFeatureSetUplinkPerCC.

In operation 1 j-15, the terminal may perform an RRC connectionreconfiguration process with the base station. The base station mayperform an RRC connection reconfiguration process (RRC reconfiguration)with the terminal for normal uplink configuration. The base station maytransmit an RRC connection reconfiguration message (anRRCReconfiguration message) to the terminal. The RRC connectionreconfiguration message may include configuration information about atleast one UL BWP for an uplink of one serving cell. For example,UplinkConfig may be included in uplinkConfig included inServingCellConfig IE, and at least one UL BWP may be configured in theuplink of one serving cell. Also, maxRank may be configured for each ULBWP (maxRank in PUSCH-Config in BWP-UplinkDedicated in uplinkConfig inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for an uplink of one serving cell(maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig inServingCellConfig). Upon receiving the RRC connection reconfigurationmessage, the terminal may apply the configuration information includedin the RRC connection reconfiguration message.

In operation 1 j-20, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). The maximum number of layers may be determined through thefollowing method.

-   -   When maxMIMO-Layers are configured for the serving cell        (maxMIMO-Layers in PUSCH-ServingCellConfig in uplinkConfig in        ServingCellConfig), the terminal may apply the maxMIMO-Layers        configured for all UL BWPs of the serving cell as the maximum        number of layers.    -   When maxMIMO-Layers are not configured for the serving cell and        maxRank is configured for one or more UL BWPs, the terminal may        apply the greatest maxRank for all UL BWPs of the serving cell        (the maximum value of maxRank across all UL BWPs of the serving        cell) as the maximum number of layers.    -   When maxMIMO-Layers and maxRank are not configured for the        serving cell, the terminal may apply the maximum number of        layers supported by the terminal for the serving cell for a        PUSCH transmission operation as the maximum number of layers.

In operation 1 j-25, the terminal may perform a PUSCH transmissionoperation. For example, the terminal may perform a PUSCH transmissionoperation by determining a rate matching and a TBS size for PUSCHtransmission in the UL BWP by applying the maximum number of layersdetermined in operation 1 j-20.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the serving cell.

In operation 1 j-30, the terminal may perform an RRC connectionreconfiguration process (RRC reconfiguration) with the base station toconfigure a supplementary uplink. The base station may transmit an RRCconnection reconfiguration message (an RRCReconfiguration message) tothe terminal. The RRC connection reconfiguration message may includeconfiguration information about at least one UL BWP for a supplementaryuplink of one serving cell. For example, UplinkConfig may be included insupplementaryUplink included in ServingCellConfig 1E, and at least oneUL BWP may be configured in the supplementary uplink of one servingcell. Also, maxRank may be configured for each UL BWP (maxRank inPUSCH-Config in BWP-UplinkDedicated in supplementaryUplink inServingCellConfig). The RRC connection reconfiguration message mayinclude a maxMIMO-Layers parameter for a supplementary uplink of oneserving cell (maxMIMO-Layers in PUSCH-ServingCellConfig insupplementaryUplink in ServingCellConfig). Upon receiving the RRCconnection reconfiguration message, the terminal may apply theconfiguration information included in the RRC connection reconfigurationmessage.

In operation 1 j-35, the terminal may determine a maximum number oflayers for one transport block (TB) for an uplink-shared channel(UL-SCH). According to various embodiments of the disclosure, themaximum number of layers may be determined by applying at least one ofthe following methods.

-   -   According to an embodiment of the disclosure, when the        maxMIMO-Layers is configured in the uplinkConfig and the        maxMIMO-Layers is not configured in the supplementaryUplink for        the serving cell but the maxRank is configured for one or more        (supplementary) UL BWPs for the supplementaryUplink, the        terminal may apply the maxMIMO-Layers value signaled in the        uplinkConfig as the maximum number of layers for all UL BWPs for        the (normal) uplink of the serving cell and apply the greatest        maxRank among the maxRank values of the (supplementary) UL BWPs        signaled in the supplementaryUplink as the maximum number of        layers for all UL BWPs for the supplementary uplink of the        serving cell (operation 1 j-40).

In operation 1 j-50, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers value applied to the uplink of theserving cell and the maxRank applied to the supplementary uplink inoperation 1 j-40. For example, the terminal may determine a ratematching and a TBS size for PUSCH transmission in the UL BWP operatingin the normal uplink by applying the maximum number of layers determinedfor the uplink of the serving cell (maxMIMO-Layers in uplinkConfig). Theterminal may perform a PUSCH transmission operation based on thedetermined rate matching and TBS size.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the uplink of the serving cell.

According to an embodiment of the disclosure, the terminal may determinea rate matching and a TBS size for PUSCH transmission in the UL BWPoperating in the supplementary uplink by applying the maximum number oflayers determined for the supplementary uplink of the serving cell (themaximum value of maxRank across all UL BWPs in supplementaryUplink). Theterminal may perform a PUSCH transmission operation based on thedetermined rate matching and TBS size.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the supplementary uplink of the serving cell.

-   -   According to an embodiment of the disclosure, when the        maxMIMO-Layers is configured in the supplementaryUplink and the        maxMIMO-Layers is not configured in the uplinkConfig for the        serving cell but the maxRank is configured for one or more        (normal) UL BWPs for the normal uplink, the terminal may apply        the maxMIMO-Layers value signaled in the supplementaryUplink as        the maximum number of layers for all UL BWPs for the        supplementary uplink of the serving cell and apply the greatest        maxRank among the maxRank values for the (normal) UL BWPs        signaled in the uplinkConfig as the maximum number of layers for        all UL BWPs for the (normal) uplink of the serving cell        (operation 1 j-45).

In operation 1 j-50, the terminal may perform a PUSCH transmissionoperation based on the maxMIMO-Layers value applied to the supplementaryuplink of the serving cell and the maxRank applied to the (normal)uplink in operation 1 j-45. For example, the terminal may determine arate matching and a TBS size for PUSCH transmission in the UL BWPconfigured for the supplementary uplink by applying the maximum numberof layers determined for the supplementary uplink of the serving cell(maxMIMO-Layers in supplementaryUplink). The terminal may perform aPUSCH transmission operation based on the determined rate matching andTBS size.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the supplementary uplink of the serving cell.

According to an embodiment of the disclosure, the terminal may determinea rate matching and a TBS size for PUSCH transmission in the UL BWPconfigured in the (normal) uplink by applying the maximum number oflayers determined for the (normal) uplink of the serving cell (themaximum value of maxRank across all UL BWPs in uplinkConfig). Theterminal may perform a PUSCH transmission operation based on thedetermined rate matching and TBS size.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the TBS size by performing a rate matching byapplying the determined maximum number of layers.

According to an embodiment of the disclosure, when performing an LBRM,which limits the number of parity bits that may be transmitted among allparity bits generated by LDPC coding for a particular input, theterminal may determine the size of the buffer of the LBRM by applyingthe determined maximum number of layers.

According to an embodiment of the disclosure, in the case of performingan FBRM for transmitting all parity bits generated by LDPC coding for aparticular input, the terminal may determine the TBS size by performinga rate matching based on the number of layers configured for each BWPfor the (normal) uplink of the serving cell.

FIG. 1K is a diagram illustrating a method of signaling maxMIMO-Layerswhen a base station configures an uplink configuration (uplinkConfig)and an additional uplink configuration (supplementaryUplink) to an RRCconnection mode terminal for one serving cell according to an embodimentof the disclosure.

Referring to FIG. 1K, the base station may transmit an uplinkConfig inan RRCReconfiguration message through an RRC connection reconfigurationprocess to configure a normal uplink to the RRC connection modeterminal. In this case, maxMIMO-Layers may be signaled to the terminalthrough the uplinkConfig for one serving cell (operation 1 k-05).

The base station may transmit a supplementaryUplink in anRRCReconfiguration message to the terminal in the RRC connection modethrough an RRC connection reconfiguration process in order to configurea supplementary uplink for the serving cell. When the base stationsignals the maxMIMO-Layers in the uplinkConfig for the serving cell tothe terminal in operation 1 k-05, the base station may signal a valueequal to the maxMIMO-Layers signaled in operation 1 k-05 in thesupplementaryUplink. Alternatively, when the base station signals themaxMIMO-Layers in the uplinkConfig for the serving cell to the terminalin operation 1 k-05, the base station may signal a value different fromthe maxMIMO-Layers signaled in operation 1 k-05 in thesupplementaryUplink (operation 1 k-10).

FIG. 1L is a diagram illustrating a structure of a terminal according toan embodiment of the disclosure.

Referring to FIG. 1L, the terminal may include a radio frequency (RF)processor 1 l-10, a baseband processor 1 l-20, a storage 1 l-30, and acontroller 1 l-40.

According to an embodiment of the disclosure, the RF processor 1 l-10may perform functions for transmitting or receiving signals throughwireless channels, such as band conversion and amplification of signals.That is, the RF processor 1 l-10 may up-convert a baseband signalprovided from the baseband processor 1 l-20 into an RF band signal andtransmit the same through an antenna and may down-convert an RF bandsignal received through the antenna into a baseband signal. For example,the RF processor 1 l-10 may include a transmission filter, a receptionfilter, an amplifier, a mixer, an oscillator, a digital-to-analogconverter (DAC), and an analog-to-digital converter (ADC). Although onlyone antenna is illustrated in FIG. 1L, the terminal may include aplurality of antennas.

Also, the RF processor 1 l-10 may include a plurality of RF chains. Inaddition, the RF processor 1 l-10 may perform beamforming. Forbeamforming, the RF processor 1 l-10 may adjust the phase and magnitudeof each of the signals transmitted or received through a plurality ofantennas or antenna elements. Also, the RF processor may performmultiple-input and multiple-output (MIMO) and may receive multiplelayers when performing a MIMO operation. Under the control of thecontroller, the RF processor 1 l-10 may perform reception beam sweepingby suitably configuring a plurality of antennas or antenna elements ormay adjust the direction and width of a reception beam so that thereception beam may be coordinated with a transmission beam.

The baseband processor 1 l-20 may perform a conversion function betweena baseband signal and a bitstream according to the physical layerstandard of the system. For example, during data transmission, thebaseband processor 1 l-20 may generate complex symbols by encoding andmodulating a transmission bitstream. Also, during data reception, thebaseband processor 1 l-20 may restore a reception bitstream bydemodulating and decoding the baseband signal provided from the RFprocessor 1 l-10. For example, according to an OFDM scheme, during datatransmission, the baseband processor 1 l-20 may generate complex symbolsby encoding and modulating a transmission bitstream, map the complexsymbols to subcarriers, and then configure OFDM symbols through aninverse fast Fourier transform (IFFT) operation and cyclic prefix (CP)insertion. Also, during data reception, the baseband processor 1 l-20may divide the baseband signal provided from the RF processor 1 l-10into OFDM symbol units, restore signals mapped to the subcarriersthrough a fast Fourier transform (FFT) operation, and then restore areception bitstream through demodulation and decoding.

The baseband processor 1 l-20 and the RF processor 1 l-10 may transmitand receive signals as described above. Accordingly, the basebandprocessor 1 l-20 and the RF processor 1 l-10 may be referred to as atransmitter, a receiver, a transceiver, or a communicator. In addition,at least one of the baseband processor 1 l-20 or the RF processor 1 l-10may include a plurality of communication modules to support a pluralityof different radio access technologies. Also, at least one of thebaseband processor 1 l-20 or the RF processor 1 l-10 may include aplurality of communication modules to process signals of differentfrequency bands. For example, the different radio access technologiesmay include LTE networks, NR networks, and the like. Also, the differentfrequency bands may include a super high frequency (SHF) (e.g., 2.2 GHzor 2 GHz) band and a millimeter wave (e.g., 60 GHz) band.

The storage 1 l-30 may store data such as a basic program, anapplication program, or configuration information for operation of theterminal. The storage 1 l-30 may provide the stored data at the requestof the controller 1 l-40.

The controller 1 l-40 may control overall operations of the terminal.For example, the controller 1 l-40 may transmit/receive signals throughthe baseband processor 1 l-20 and the RF processor 1 l-10. Also, thecontroller 1 l-40 may write/read data into/from the storage 1 l-30. Forthis purpose, the controller 1 l-40 may include at least one processor.For example, the controller 1 l-40 may include a communication processor(CP) 1 l-42 for performing control for communication and an applicationprocessor (AP) for controlling an upper layer such as an applicationprogram.

FIG. 1M is a diagram illustrating a structure of a base stationaccording to an embodiment of the disclosure.

Referring to FIG. 1M, the base station may include one or moretransmission reception points (TRPs).

According to an embodiment of the disclosure, the base station mayinclude an RF processor 1 m-10, a baseband processor 1 m-20, a backhaulcommunicator 1 m-30, a storage 1 m-40, and a controller 1 m-50.

The RF processor 1 m-10 may perform functions for transmitting orreceiving signals through wireless channels, such as band conversion andamplification of signals. That is, the RF processor 1 m-10 mayup-convert a baseband signal provided from the baseband processor 1 m-20into an RF band signal and transmit the same through an antenna and maydown-convert an RF band signal received through the antenna into abaseband signal. For example, the RF processor 1 m-10 may include atransmission filter, a reception filter, an amplifier, a mixer, anoscillator, a DAC, and an ADC. Although only one antenna is illustratedin FIG. 1M, the base station may include a plurality of antennas.

Also, the RF processor 1 m-10 may include a plurality of RF chains. Inaddition, the RF processor 1 m-10 may perform beamforming. Forbeamforming, the RF processor 1 m-10 may adjust the phase and magnitudeof each of the signals transmitted/received through a plurality ofantennas or antenna elements. The RF processor may perform a downlinkMIMO operation by transmitting one or more layers.

The baseband processor 1 m-20 may perform a conversion function betweena baseband signal and a bitstream according to the physical layerstandard of a first radio access technology. For example, during datatransmission, the baseband processor 1 m-20 may generate complex symbolsby encoding and modulating a transmission bitstream. Also, during datareception, the baseband processor 1 m-20 may restore a receptionbitstream by demodulating and decoding the baseband signal provided fromthe RF processor 1 m-10. For example, according to the OFDM scheme,during data transmission, the baseband processor 1 m-20 may generatecomplex symbols by encoding and modulating a transmission bitstream, mapthe complex symbols to subcarriers, and then configure OFDM symbolsthrough an IFFT operation and CP insertion. Also, during data reception,the baseband processor 1 m-20 may divide the baseband signal providedfrom the RF processor 1 m-10 into OFDM symbol units, restore signalsmapped to the subcarriers through an FFT operation, and then restore areception bitstream through demodulation and decoding.

The baseband processor 1 m-20 and the RF processor 1 m-10 may transmitand receive signals as described above. Accordingly, the basebandprocessor 1 m-20 and the RF processor 1 m-10 may be referred to as atransmitter, a receiver, a transceiver, a communicator, or a wirelesscommunicator.

The backhaul communicator 1 m-30 may provide an interface forcommunicating with other nodes in the network.

The storage 1 m-40 may store data such as a basic program, anapplication program, or configuration information for operation of themain base station. Particularly, the storage 1 m-40 may storeinformation about a bearer allocated to a connected terminal, ameasurement result reported from the connected terminal, or the like.Also, the storage 1 m-40 may store information that is a reference fordetermining whether to provide or terminate multiple connections to theterminal. The storage 1 m-40 may provide the stored data at the requestof the controller 1 m-50.

The controller 1 m-50 may control overall operations of the main basestation. For example, the controller 1 m-50 may transmit/receive signalsthrough the baseband processor 1 m-20 and the RF processor 1 m-10 orthrough the backhaul communicator 1 m-30. Also, the controller 1 m-50may write/read data into/from the storage 1 m-40. For this purpose, thecontroller 1 m-50 may include at least one processor 1 m-52. Thebaseband processor 1 m-20 and the RF processor 1 m-10 may be referred toas a transmitter, a receiver, a transceiver, a communicator, or awireless communicator.

FIGS. 1N and 1O are diagrams illustrating an example of wirelesstransmission and reception paths according to various embodiments of thedisclosure.

Referring to FIGS. 1N and 1O, a transmission path 200 may be describedas being implemented in the terminal, and a reception path 250 may bedescribed as being implemented in the base station (gNB). However, thereception path 250 may be implemented in the terminal, and thetransmission path 200 may be implemented in the base station. Accordingto an embodiment of the disclosure, the reception path 250 may beconfigured to receive one or two codewords depending on the number oflayers transmitted, as described in embodiments of the disclosure.

The transmission path 200 may include a channel coding and modulationblock 205, a serial-to-parallel (S-to-P) block 210, a size N inversefast Fourier transform (IFFT) block 215, a parallel-to-Serial (P-to-S)block 220, a cyclic prefix (CP) addition block 225, and an up-converter(UC) 230. The reception path 250 may include a down-converter (DC) 255,a CP removal block 260, a serial-to-parallel (S-to-P) block 265, a sizeN fast Fourier transform (FFT) block 270, a parallel-to-serial (P-to-S)block 275, and a channel decoding and demodulation block 280.

In the transmission path 200, the channel coding and modulation block205 may receive a set of information bits, apply coding (e.g.,convolutional, turbo, polar, or LDPC coding), and modulate the inputbits (e.g., quadrature phase shift keying (QPSK) or quadrature amplitudemodulation (QAM)) to generate a sequence of frequency domain modulationsymbols. The serial-to-parallel block 210 may convert (e.g.,demultiplex) the serially modulated symbols into parallel data togenerate N parallel symbol streams, where N is an IFFT/FFT size used inthe base station and the terminal. The size N IFFT block 215 may performan IFFT operation on the N parallel symbol streams to generatetime-domain output signals. The parallel-to-serial block 220 may convert(e.g., multiplex) the parallel time-domain output symbols from the sizeN IFFT block 215 to generate a serial time-domain signal. The CPaddition block 225 may insert a CP into the time-domain signal. Theup-converter 230 may modulate (e.g., up-convert) the output of the CPaddition block 225 to an RF frequency for transmission on a radiochannel. Also, this signal may be filtered in the baseband beforeconversion to the RF frequency.

The RF signal transmitted from the terminals may arrive at the basestation after passing through the radio channel, and inverse operationsfor the operations in the terminal may be performed in the base station.The down-converter 255 may down-convert the received signal to abaseband frequency, and the CP removal block 260 may remove the CP togenerate a serial time-domain baseband signal. The serial-to-parallelblock 265 may convert the time-domain baseband signal into paralleltime-domain signals. The size N FFT block 270 may perform an FFTalgorithm to generate N parallel frequency domain signals. Theparallel-to-serial block 275 may convert the parallel frequency-domainsignals into a sequence of modulated data symbols. The channel decodingand demodulation block 280 may restore an original input data stream bydemodulating the modulated symbols and then decoding the resultsthereof.

As described below in more detail, the transmission path 200 or thereception path 250 may perform signaling for multistream transmission.Each of the base stations may implement the transmission path 200similar to the downlink transmission to the terminals or may implementthe reception path 250 similar to the uplink reception from theterminals. Similarly, each of the terminals may implement thetransmission path 200 similar to the uplink transmission to the basestations or may implement the reception path 250 similar to the downlinkreception from the base stations.

Each of the components in FIGS. 1N and 1O may be implemented by usingonly hardware or by using a combination of hardware andsoftware/firmware. As a particular example, at least some of thecomponents in FIGS. 1N and 1O may be implemented by software, whileother components may be implemented by configurable hardware or amixture of software and configurable hardware. For example, the FFTblock 270 and the IFFT block 215 may be implemented as configurablesoftware algorithms, where the value of the size N may vary according tothe implementation thereof.

Also, although it has been described that the FFT and the IFFT are used,this is merely for illustrative purposes and should not be construed aslimiting the scope of the disclosure. Other types of modifications suchas discrete Fourier transform (DFT) functions and inverse discreteFourier transform (IDFT) functions may be used. As for DFT and IDFTfunctions, the value of a variable N may be any integer (e.g., 1, 2, 3,or 4), and as for FFT and IFFT functions, the value of a variable N maybe any integer that is the power of 2 (e.g., 1, 2, 4, 8, or 16).

Although FIGS. 1N and 1O illustrate examples of wireless transmissionand reception paths, various modifications may be made in FIGS. 1N and1O. For example, various components in FIGS. 1N and 1O may be combined,further subdivided, or omitted, and additional components may be addedaccording to particular needs. Also, FIGS. 1N and 1O are to describeexamples of types of transmission and reception paths that may be usedin wireless networks. Any other suitable architectures may be used tosupport wireless communications in wireless networks.

FIG. 1P is a diagram illustrating an example embodiment for a bit-leveland a symbol-level processing of a terminal or a base station accordingto an embodiment of the disclosure.

Referring to FIG. 1P, bit-level and symbol-level processing may bedescribed in an embodiment 1100 of FIG. 1P. A transport block (TB) 1101may be processed by a series of bit-level operations 1102 including atleast one of code block (CB) segmentation 1103, channel coding, ratematching, or channel interleaver (only for UL). The output of bit-levelprocessing 1104 associated with one TB and one CW may be processed by aseries of symbol-level operations 1105 including at least one ofmodulation mapping, layer mapping 1106, precoding, or RE mapping.

The methods according to the embodiments of the disclosure described inthe specification or the claims may be implemented by hardware,software, or a combination thereof.

When the methods are implemented by software, a computer-readablestorage medium may be provided to store one or more programs (softwaremodules). The one or more programs stored in the computer-readablestorage medium may be configured for execution by one or more processorsin an electronic device. The one or more programs may includeinstructions for causing the electronic device to execute the methodsaccording to the embodiments of the disclosure described in thespecification or the claims.

These programs (software modules or software) may be stored in randomaccess memories (RAMs), nonvolatile memories including flash memories,read only memories (ROMs), electrically erasable programmable ROMs(EEPROMs), magnetic disc storage devices, compact disc-ROMs (CD-ROMs),digital versatile discs (DVDs), other types of optical storage devices,or magnetic cassettes. Alternatively, the programs may be stored in amemory configured by a combination of some or all of such storagedevices. Also, each of the memories may be provided in plurality.

Also, the programs may be stored in an attachable storage device thatmay be accessed through a communication network such as Internet,Intranet, local area network (LAN), wide LAN (WLAN), or storage areanetwork (SAN), or through a communication network configured by anycombination thereof. Such a storage device may be connected through anexternal port to an apparatus performing an embodiment of thedisclosure. Also, a separate storage device on a communication networkmay be connected to an apparatus performing an embodiment of thedisclosure.

In the above particular embodiments of the disclosure, the componentsincluded in the disclosure are expressed in the singular or pluralaccording to the particular embodiments of the disclosure. However, thesingular or plural expressions are selected suitably according to thepresented situations for convenience of description, the disclosure isnot limited to the singular or plural components, and the componentsexpressed in the plural may even be configured in the singular or thecomponents expressed in the singular may even be configured in theplural.

While the disclosure has been shown described with reference to variousembodiments thereof, it will be understood by those skilled in the artthat various changes in form and details may be made therein withoutdeparting from the spirit and scope of the disclosure as defined by theappended claims and their equivalents.

What is claimed is:
 1. A method of a terminal in a wirelesscommunication system, the method comprising: transmitting, to a basestation, capability information including a first maximum number ofmultiple-input and multiple output (MIMO) layers of a first carrier anda second maximum number of MIMO layers of a second carrier uplink,wherein the first carrier is different from the second carrier;receiving, from the base station, a radio resource control (RRC) messageincluding configuration information for a normal uplink including athird maximum number of MIMO layers and information related to abandwidth part (BWP) of the normal uplink; in case that the RRC messageincludes configuration information for a supplementary uplink,identifying a fourth maximum number of MIMO layers for the supplementaryuplink based on the configuration information for the supplementaryuplink, the configuration information for the supplementary uplinkincluding the fourth maximum number of MIMO layers and informationrelated on BWP of the supplementary uplink; and transmitting, to thebase station, a physical uplink shared channel (PUSCH) using one of thenormal uplink and the supplementary uplink, wherein the normal uplink isusing the first carrier and the supplementary uplink is using the secondcarrier, and wherein the normal uplink is configured based on the thirdmaximum number of MIMO layers and the information related on BWP of thenormal uplink, and the supplementary uplink is configured based on thefourth maximum number of MIMO layers and the information related on BWPof the supplementary uplink.
 2. The method of claim 1, furthercomprising identifying the third maximum number of MIMO layers for thenormal uplink, based on the configuration information for the normaluplink.
 3. The method of claim 1, wherein the identifying of the fourthmaximum number of MIMO layers comprises, in case that maximum MIMOlayers information and maximum rank information are not configured inthe configuration information for the supplementary uplink, identifyingthe maximum number of layers for the PUSCH supported by the terminal fora serving cell to be the fourth maximum number of MIMO layers for theBWP of the supplementary uplink.
 4. The method of claim 1, wherein theconfiguration information for the normal uplink and the configurationinformation for the supplementary uplink are for a serving cell.
 5. Aterminal in a wireless communication system, the terminal comprising: atransceiver; and at least one controller configured to: transmit, to abase station, capability information including a first maximum number ofmultiple-input and multiple output (MIMO) layers of a first carrier anda second maximum number of MIMO layers of a second carrier uplink,wherein the first carrier is different from the second carrier, receive,from the base station, a radio resource control (RRC) message includingconfiguration information for a normal uplink including a third maximumnumber of MIMO layers and information related to a bandwidth part (BWP)of the normal uplink, in case that the RRC message includesconfiguration information for a supplementary uplink including, identifya fourth maximum number of MIMO layers for the supplementary uplinkbased on the configuration information for the supplementary uplink, theconfiguration information for the supplementary uplink including thefourth maximum number of MIMO layers and information related on BWP ofthe supplementary uplink, and transmit, to the base station, a physicaluplink shared channel (PUSCH) using one of the normal uplink and thesupplementary uplink, wherein the normal uplink is configured based onthe third maximum number of MIMO layers and the information related onBWP of the normal uplink, and the supplementary uplink is configuredbased on the fourth maximum number of MIMO layers and the informationrelated on BWP of the supplementary uplink.
 6. The terminal of claim 5,wherein the at least one controller further configured to identify thethird maximum number of MIMO layers for the normal uplink, based on theconfiguration information for the normal uplink.
 7. The terminal ofclaim 5, wherein the at least one controller is further configured to,in case that maximum MIMO layers information and maximum rankinformation are not configured in the configuration information for thesupplementary uplink, identify the maximum number of layers for thePUSCH supported by the terminal for a serving cell to be the secondmaximum number of MIMO layers for the BWP of the supplementary uplink.8. The terminal of claim 5, wherein the configuration information forthe normal uplink and the configuration information for thesupplementary uplink are for a serving cell.